Reduced-size interfaces for managing alerts

ABSTRACT

An electronic device with a display can receive an alert comprising information, and in response to receiving the alert, issue a perceptual output. The device can detect a user input and determine whether the user input was detected within a predetermined time interval after the perceptual output. In accordance with a determination that the user input was detected within the predetermined time interval, the device can display a notification on the display, wherein the notification comprises a first portion of the information. If the device continues to detect the user input after a second predetermined time period, the device can display a second portion of the information, where the second portion is different from the first portion.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/838,235, entitled “Reduced-Size Interfaces for Managing Alerts,”filed on Aug. 27, 2015, which claims priority to U.S. Provisional PatentApplication Ser. No. 62/044,894, entitled “Reduced-Size Interfaces ForManaging Alerts,” filed on Sep. 2, 2014, and to U.S. ProvisionalApplication Ser. No. 62/129,818, entitled “Reduced-Size Interfaces ForManaging Alerts,” filed on Mar. 7, 2015. The content of theseapplications is hereby incorporated by reference for all purposes.

This application relates to U.S. Provisional Patent Application Ser. No.62/129,924 titled “Reduced-Size Notification Interface,” filed Mar. 8,2015; U.S. Provisional Patent Application Ser. No. 62/044,953 titled“Reduced-Size Notification Interface,” filed Sep. 2, 2014; U.S.Provisional Patent Application Ser. No. 62/129,903 entitled “UserInterface For Receiving User Input,” filed Mar. 8, 2015; U.S.Provisional Patent Application Ser. No. 62/127,800 titled “UserInterface For Receiving User Input,” filed Mar. 3, 2015; U.S.Provisional Patent Application Ser. No. 62/044,923 entitled “UserInterface For Receiving User Input,” filed Sep. 2, 2014; U.S.Provisional Patent Application Ser. No. 62/026,532, “Raise GestureDetection in a Device,” filed Jul. 18, 2014; International PatentApplication Serial No. PCT/US2013/040061, “Device, Method, and GraphicalUser Interface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013; and U.S. Provisional PatentApplication Ser. No. 62/044,894, filed Sep. 2, 2014. The contents ofthese applications are hereby incorporated by reference in theirentirety.

FIELD

The disclosed examples relate generally to user interfaces of electronicdevices.

BACKGROUND

Reduced-size electronic devices (e.g., devices that are smaller thantypical cellular phones) that are configured to be worn by a user canallow a user to view and respond to various types of alerts, such astext messages, emails, voicemails, and calendar alerts. User interfacesthat enable a reduced-size electronic device to be efficiently used forviewing and responding to alerts are desirable.

SUMMARY

In accordance with some embodiments, a method is performed at anelectronic device with a display. The method includes receiving an alertcomprising information, and in response to receiving the alert, issuinga perceptual output. The method includes detecting a user input anddetermining whether the user input was detected within a predeterminedtime interval after the perceptual output. The method includes, inaccordance with a determination that the user input was detected withinthe predetermined time interval, displaying a notification on thedisplay, wherein the notification comprises a first portion of theinformation.

In accordance with some embodiments, a method is performed at anelectronic device with a display. The method includes receiving a firstalert and a second alert. The method includes, in response to receivingthe first alert and the second alert, determining whether the firstalert and second alert meet a grouping criteria. The method includes, inresponse to a determination that the first alert and the second alertmeet the grouping criteria, displaying a grouped notificationrepresenting the first alert and the second alert. The method includes,in response to a determination that the first alert and the second alertdo not meet the grouping criteria, displaying a first notificationrepresenting the first alert, and replacing display of the firstnotification with display of a second notification representing thesecond alert.

In accordance with some embodiments, a method is performed at anelectronic device that is actively displaying content. The methodincludes receiving an alert comprising information. The method includes,in response to receiving the alert, displaying a notification banneracross a portion of the display, wherein the notification bannercomprises a first portion of the information and wherein at least aportion of the content continues to be displayed. The method includesdetecting a contact on the display at a location corresponding to thenotification banner, and in response to detecting the contact,displaying a second portion of the information, wherein the secondportion is different from the first portion.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a display cause the electronic device to:receive an alert comprising information; in response to receiving thealert, issue a perceptual output; detect a user input; determine whetherthe user input was detected within a predetermined time interval afterthe perceptual output; and in accordance with a determination that theuser input was detected within the predetermined time interval, displaya notification on the display, wherein the notification comprises afirst portion of the information.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a display cause the electronic device to:receive a plurality of alerts; in response to receiving the plurality ofalerts, determine whether the plurality of alerts meet a groupingcriteria; in accordance with a determination that the plurality ofalerts meet the grouping criteria, display a grouped notificationrepresenting the plurality of alerts; and, in response to adetermination that the plurality of alerts do not meet the groupingcriteria, display a plurality of notifications representing theplurality of alerts.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: while actively displaying content, receive an alertcomprising information; in response to receiving the alert, display of anotification banner across a portion of the display, wherein thenotification banner comprises a first portion of the information andwherein at least a portion of the content continues to be displayed;detect a contact on the touch-sensitive display at a locationcorresponding to the notification banner; and, in response to detectingthe contact, display of a second portion of the information, wherein thesecond portion is different from the first portion.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a display cause the electronic device to:receive an alert comprising information; in response to receiving thealert, issue a perceptual output; detect a user input; determine whetherthe user input was detected within a predetermined time interval afterthe perceptual output; and in accordance with a determination that theuser input was detected within the predetermined time interval, displaya notification on the display, wherein the notification comprises afirst portion of the information.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a display cause the electronic device to:receive a plurality of alerts; in response to receiving the plurality ofalerts, determine whether the plurality of alerts meet a groupingcriteria; in accordance with a determination that the plurality ofalerts meet the grouping criteria, display a grouped notificationrepresenting the plurality of alerts; and, in response to adetermination that the plurality of alerts do not meet the groupingcriteria, display a plurality of notifications representing theplurality of alerts.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display cause the electronicdevice to: while actively displaying content, receive an alertcomprising information; in response to receiving the alert, display of anotification banner across a portion of the display, wherein thenotification banner comprises a first portion of the information andwherein at least a portion of the content continues to be displayed;detect a contact on the touch-sensitive display at a locationcorresponding to the notification banner; and, in response to detectingthe contact, display of a second portion of the information, wherein thesecond portion is different from the first portion.

An electronic device, comprising: a display; one or more processors; amemory; and one or more programs, wherein the one or more programs arestored in the memory and configured to be executed by the one or moreprocessors, the one or more programs including instructions for:receiving an alert comprising information, and in response to receivingthe alert, issuing a perceptual output; detecting a user input anddetermining whether the user input was detected within a predeterminedtime interval after the perceptual output; in accordance with adetermination that the user input was detected within the predeterminedtime interval, displaying a notification on the display, wherein thenotification comprises a first portion of the information.

An electronic device, comprising: a display; one or more processors; amemory; and one or more programs, wherein the one or more programs arestored in the memory and configured to be executed by the one or moreprocessors, the one or more programs including instructions for:receiving a first alert and a second alert and, in response to receivingthe first alert and the second alert, determining whether the firstalert and second alert meet a grouping criteria; in response to adetermination that the first alert and the second alert meet thegrouping criteria, displaying a grouped notification representing thefirst alert and the second alert; in response to a determination thatthe first alert and the second alert do not meet the grouping criteria,displaying a first notification representing the first alert, andreplacing display of the first notification with display of a secondnotification representing the second alert.

An electronic device, comprising: a touch-sensitive display; one or moreprocessors; a memory; and one or more programs, wherein the one or moreprograms are stored in the memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: receiving an alert comprising information and in response toreceiving the alert, displaying a notification banner across a portionof the display, wherein the notification banner comprises a firstportion of the information and wherein at least a portion of the contentcontinues to be displayed; detecting a contact on the display at alocation corresponding to the notification banner, and in response todetecting the contact, displaying a second portion of the information,wherein the second portion is different from the first portion.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 5C illustrates detection of contacts with intensity sensors.

FIG. 5D illustrates assigning an aggregate intensity to contacts.

FIGS. 5E-5H illustrate detection of a gesture having an intensity ofcontact.

FIGS. 6A-6C illustrate exemplary user interfaces.

FIG. 7 illustrates an exemplary user interface.

FIG. 8 illustrates an exemplary user interface.

FIG. 9 illustrates an exemplary user interface.

FIG. 10 illustrates an exemplary user interface.

FIG. 11 illustrates an exemplary user interface.

FIGS. 12A-C illustrate an exemplary user interface.

FIGS. 13A-B illustrates an exemplary user interface.

FIG. 14 illustrates an exemplary user interface.

FIG. 15 illustrates an exemplary user interface.

FIG. 16 illustrates an exemplary user interface.

FIG. 17 illustrates an exemplary user interface.

FIG. 18 illustrates an exemplary user interface.

FIG. 19 illustrates an exemplary user interface.

FIG. 20 illustrates an exemplary user interface.

FIG. 21 illustrates an exemplary user interface.

FIG. 22 illustrates an exemplary user interface.

FIGS. 23A-23C illustrate exemplary user interfaces.

FIG. 24 illustrates an exemplary user interface.

FIG. 25 illustrates an exemplary process for managing alerts.

FIG. 26 illustrates an exemplary process for managing alerts.

FIG. 27 illustrates an exemplary process for managing alerts.

FIGS. 28-31 illustrate exemplary functional block diagrams of electronicdevices in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

As discussed above, a reduced-size personal electronic device that isconfigured to be worn by a user can enable a user to view and respond tovarious alerts, such as text messages, emails, voicemails, audiomessages, stock alerts, clock alarms, calendar alerts, fitness alerts,store coupons or loyalty program alerts, for example, via userinterfaces. There are, however, several challenges associated withviewing and responding to alerts on a reduced-size device. For example,user interface approaches designed for larger screens may not work wellon electronic devices having reduced-size screens. The smaller screensize may make it challenging to read textual content associated with analert, for example, or to provide accurate inputs to a touchscreen.There may be insufficient screen space to display detailed device usageinstructions, thus making it important that the user interfaces beintuitive to learn and use. The limited screen size may make displayingmultiple tiled screens impractical; thus, replacing one screen withanother, and limiting the amount of information displayed on a singlescreen, may be a more effective user interface strategy.

In addition to the above usability concerns, there may be privacyconcerns if the reduced-size electronic device is worn externally by theuser (by attaching it to a shirt, belt, bracelet, or necklace, forexample) rather than carried in a pocket, case, or purse, as is commonwith larger electronic devices such as cellular phones or laptops. Theuser may be concerned that others who are nearby will be able to viewthe alerts, so it may be desirable that such user interfaces allow theuser to control when and how much of the alert content is displayed.Furthermore, if the device is worn by the user and is thus in closercontact with the user than, for example, a cellular phone, it may bedesirable that such user interfaces do not annoy the user with frequentinterruptions. Ideally, the user interface should make it quick, easy,and intuitive for a user to view and respond to alerts on a reduced-sizepersonal electronic device. Such techniques can reduce the cognitiveburden on a user who uses alerts, thereby enhancing productivity.Further, such techniques can reduce processor and battery powerotherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for managing alertnotifications. FIGS. 6A-24 illustrate exemplary user interfaces formanaging alert notifications. The user interfaces in the figures arealso used to illustrate the processes described below, including theprocesses in FIGS. 25-27.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a “touch-sensitive display system.” Device 100includes memory 102 (which optionally includes one or morecomputer-readable storage mediums), memory controller 122, one or moreprocessing units (CPUs) 120, peripherals interface 118, RF circuitry108, audio circuitry 110, speaker 111, microphone 113, input/output(I/O) subsystem 106, other input control devices 116, and external port124. Device 100 optionally includes one or more optical sensors 164.Device 100 optionally includes one or more contact intensity sensors 165for detecting intensity of contacts on device 100 (e.g., atouch-sensitive surface such as touch-sensitive display system 112 ofdevice 100). Device 100 optionally includes one or more tactile outputgenerators 167 for generating tactile outputs on device 100 (e.g.,generating tactile outputs on a touch-sensitive surface such astouch-sensitive display system 112 of device 100 or touchpad 355 ofdevice 300). These components optionally communicate over one or morecommunication buses or signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 2005/0190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.2006/0017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in its entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 may be a rotatable inputdevice or a depressible and rotatable input device, for example. Inputmechanism 508 may be a button, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514. Personalelectronic device 500 can also include haptic mechanism 542. Hapticmechanism 542 may issue a vibration or other haptic output that can beperceived by a user. In some embodiments, haptic mechanism 542 may issuehaptic outputs in a manner similar to that described for tactile outputgenerator 167 of device 100.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 2500-2700 (FIGS. 25-27).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold. Attention is now directed towards embodiments ofuser interfaces and associated processes that may be implemented on amultifunction device with a display and a touch-sensitive surface, suchas devices 100, 300, and/or 500, to improve a user's experience inmanaging alerts.

1. User Interfaces for Managing Alerts

The user interfaces for managing alerts described below are illustratedby exemplary sequences of screens that device 500 can display inresponse to receiving alerts and detecting various user inputs. In thesesequences, the arrows indicate the order in which the screens may bedisplayed.

a. Displaying Notifications

FIGS. 6A-6B depict exemplary screens 604, 612 that device 500 candisplay after receiving an alert. Initially, touchscreen 504 may beturned off or inactive. In response to receiving an alert, device 500can issue a perceptual output 602, such as an audible, visible, orhaptic output, that can be perceived by a user. In some embodiments,device 500 can issue a perceptual output by causing a haptic mechanismon device 500 to issue a haptic output. In some embodiments, device 500can issue a perceptual output by playing a sound or tone that is audibleto a user. In some embodiments, device 500 can issue a perceptual outputby displaying a visible output, such as a flashing light or an indicatoron touchscreen 504.

In some embodiments, issuing the haptic output includes issuing a firsthaptic output and, after issuing the first haptic output, issuing asecond haptic output, where the first haptic output is distinct from thesecond haptic output. In order to increase the saliency with which auser perceives a haptic output, the user may wish to receive a“pre-alert” haptic output. The first haptic output may “prime” the userfor receiving a second haptic output, which in some embodiments mayindicate specific information (e.g., the source of the alert) or beassociated with a second perceptual output (e.g., an audible or visibleoutput), as described below. For example, it may be difficult for theuser to perceive a haptic output while moving or paying attention tosomething else. Therefore, a first haptic output that “primes” the userto perceive a second haptic output (and optionally, an associated secondperceptual output) may be advantageous.

The user may wish to receive a haptic output based on the source of thealert. For example, the user may wish to receive a different hapticoutput for an email alert than for a voicemail alert. To providedistinctive haptic outputs, the device may issue a haptic output with adistinctive audible or visible output, or the device may issue a hapticoutput with a distinctive quality, e.g., a distinct intensity, duration,and/or pattern. Allowing the user to receive distinctive haptic outputsthat distinguish the source of the alert enables the user to perceivethe type of alert without having to look at the display, thus conservingbattery life. In some embodiments, the second haptic output is based onthe source of the alert. In some embodiments, the second haptic outputis issued with an audible or visible output.

In some embodiments, the first haptic output has a greater intensityand/or duration, as compared to the second haptic output. This may beadvantageous, for example, by providing a stronger haptic signal to theuser, drawing their attention to device 500 in preparation for a secondhaptic signal (e.g., one with a distinctive aspect based on the sourceof the alert, or one associated with an audible or visible output). Insome embodiments, device 500 may include a user interface (not shown)for configuring whether issuing the haptic output includes issuing afirst, “priming” haptic output. In such embodiments, if device 500 isconfigured to not issue a “priming” haptic output, issuing the hapticoutput may include issuing only one haptic output.

As depicted in FIG. 6A, in response to detecting a subsequent user inputwithin a predetermined time interval after the perceptual output 602,device 500 can display screen 604 with notification 606 representing thereceived alert. In some embodiments, the user input may be a contact ontouchscreen 504, such as a swipe or tap. In some embodiments, if device500 is worn on a user's wrist, the user input may be a signal indicativeof a user moving device 500 into a viewing position by raising orrotating their wrist. As used herein, a viewing position is a positionof device 500 in which the user can view touchscreen 504. In someembodiments, device 500 may detect a signal indicative of a user raisingor lowering their wrist as described in U.S. Provisional PatentApplication Ser. No. 62/026,532, “Raise Gesture Detection in a Device,”hereby incorporated by reference in its entirety.

The received alert includes information. Such information may include asource of the alert, an application associated with the alert, and/or atime and/or date associated with the alert, along with textual, image,or audio content, for example. In some embodiments, the notificationrepresenting the received alert comprises a portion of the alertinformation. For example, as depicted in FIG. 6A, notification 606comprises the source 610 of the alert (Jason Jones) and an applicationaffordance 608 indicating an application associated with the alert—inthis example, a text message application. (The dashed rectangle depictedon screen 604 indicates the content of the notification, but the dashedrectangle may not be displayed.) In some embodiments, in response todetecting a selection of application affordance 608, device 500 canlaunch an application associated with the alert. In some embodiments,launching an application includes displaying the application ontouchscreen 504 and opening the alert for viewing, editing, orresponding within the application.

As discussed above, device 500 can display screen 604 in response todetecting a user input within a predetermined time interval followingthe haptic output. In some embodiments, the predetermined time intervalmay range from 0 seconds to 3 minutes. In other embodiments, thepredetermined time interval may range from 0 seconds to 1 minute. In yetother embodiments, the predetermined time interval may be set by theuser, or may be determined by device 500 based on previous user behaviorsuch as an average of previous elapsed times prior to the user providingthe input.

The scenario depicted in FIG. 6A may correspond to the case when theuser, having perceived the perceptual output issued by device 500 inresponse to receiving an alert, wishes to promptly view the notificationrepresenting the received alert and therefore moves device 500 into aposition suitable for viewing touchscreen 504 (e.g., by raising theirwrist) within the predetermined time interval.

As depicted in FIG. 6B, if device 500 detects the user input after thepredetermined time interval, then device 500 can instead respond bydisplaying a clock face 612. This scenario may correspond to the casewhen the user does not wish to promptly view the notification, andraises their wrist sometime after the perceptual output 602 to viewtouchscreen 504. In some embodiments, the clock face 612 may comprise auser interface object 616 indicating the current time. In someembodiments, the clock face 612 may comprise an indication of an unreadalert 614 corresponding to the received alert, because the alert contenthas not yet been displayed. As shown in FIG. 6B, the indication 614 maybe a dot. FIG. 6C depicts another embodiment in which the indication 614is a chevron. In some embodiments, device 500 displays, in place of achevron, an arrow, triangle, or other graphical object that provides adirectional indication. Indications of unread alerts are described inmore detail below.

In some embodiments, device 500 can display a home screen rather thanclock face 612. An exemplary home screen 706 is depicted in FIG. 7. Thehome screen may include a plurality of affordances representing aplurality of applications, and may comprise an indication of an unreadalert corresponding to the received alert.

If device 500 does not detect the user input within the predeterminedtime interval after the perceptual output, device 500 may remain in itsinitial dark or inactive state without displaying screen 604. Thisscenario may correspond to the case when the user does not wish topromptly view the notification or wishes to avoid allowing others whoare nearby to view the notification, and therefore does not move device500 into position for viewing touchscreen 504 after perceiving theperceptual output.

While notification 606 is displayed, if device 500 detects a second userinput within a second predetermined time interval after displaying thenotification, device 500 can return touchscreen 504 to its initial darkor inactive state. The second user input may be, for example, a signalindicative of a user moving device 500 out of a viewing position bylowering and/or rotating their wrist. In response to detecting thesecond user input within the second predetermined time interval, device500 can return the display to its initial dark or inactive state. Thisscenario may correspond to the case where the user, having viewed thenotification, does not wish to continue viewing or interacting withdevice 500 and therefore lowers their wrist.

In some embodiments, displaying notification 606 involves displaying ananimation that slides notification 606 in a vertical direction ontotouchscreen 504. For example, device 500 may display an animation thatslides notification 606 up onto touchscreen 504 from the bottom oftouchscreen 504. Such an animation can provide a visual cue to the userthat, since the notification is “rising up” from the bottom of thescreen (for example), dismissing the alert may be performed through acontact with touchscreen 504 in the opposite direction of the animation(such as a downward swipe) to “push down” the notification. The user mayalso infer from the animation that a contact with touchscreen 504 in thesame direction as the animation (such as an upward swipe) may “pull up”(e.g., display) additional alert information, such as the body of a textmessage or additional text associated with a calendar alert. Thus,animations displayed by device 500 may provide visual cues to the userregarding potential inputs that the user can provide to device 500. Aperson of skill in the art will recognize that the animation directionfor the notification need not be in the upward direction; for example,the notification may slide down onto the touchscreen from the top of thescreen, in which case a user may infer that dismissing the notificationmay require an upward swipe. Such visual cues may improve theman-machine interface by guiding the user to apply the appropriateinputs without requiring display of detailed instructions on thereduced-size screen.

As described above, in some embodiments, device 500 can issue aperceptual output, such as by causing the haptic mechanism to issue ahaptic output, in response to receiving an alert, thereby informing theuser that an alert has been received. However, in some embodiments,device 500 can delay issuing the perceptual output in response toreceiving an alert, in order to deliver the perceptual output at a timethat is likely to be more convenient for the user. For example, device500 may delay the perceptual output until the user is relativelyinactive and thus more likely to perceive the perceptual output, ordelay the perceptual output to avoid interrupting the user while theuser is actively engaged in an activity or is sleeping. In someembodiments, in response to receiving an alert, device 500 may obtaindata from one or more motion sensors, accelerometers, heart ratemonitors, and/or other type of sensors to determine a current useractivity level—such as whether the user is currently exercising, typing,or sleeping. Device 500 can delay the perceptual output until thedetermined user activity level meets an activity criteria. In someembodiments, the activity criteria may include that the user isrelatively still (as determined by outputs from sensors on device 500),has paused from typing on a physical keyboard, has paused in speaking,or is not asleep, for example. In this manner, device 500 can issue aperceptual output to inform the user that a new alert has been receivedat a time that may be less likely to annoy to the user, while being morelikely to be perceived by the user.

After device 500 has displayed a notification, a user may choose todismiss the notification or to display the alert content (for example,the body of a text message, or text associated with a calendar alert),among other options.

b. Dismissing Notifications

FIG. 7 shows another exemplary sequence of screens that device 500 candisplay on touchscreen 504 after receiving an alert. As discussed withrespect to FIG. 6A, touchscreen 504 may initially be dark or inactive.In response to receiving an alert, device 500 can issue a perceptualoutput. As described in FIG. 6A, in response to receiving a user inputwithin a first predetermined time interval following the perceptualoutput, device 500 displays screen 604 including notification 606, whichrepresents the received alert. In this exemplary sequence, displayingnotification 606 on screen 604 involves displaying an animation thatslides notification 606 upwards from the bottom of touchscreen 504.

If while displaying notification 606 device 500 detects a contact ontouchscreen 504 that meets a dismissal criteria, then device 500 candismiss notification 606. In some embodiments, dismissing notification606 involves removing notification 606 from the display, and/orreplacing display of the notification with display of a clock face (suchas clock face 612 in FIG. 6B) or home screen 706.

In some embodiments, the contact meets the dismissal criteria if it is aswipe or flick on touchscreen 504. In some embodiments, the contactmeets the dismissal criteria if it is a swipe or flick on touchscreen504 in a specific direction; such as a swipe or flick in a directionopposite to the direction in which the animation slides the notificationonto touchscreen 504. For example, if an animation slides thenotification upwards onto touchscreen 504 from the bottom, the contactmay meet the dismissal criteria if it is a swipe on touchscreen 504 inthe downwards direction. In some embodiments, the contact may meet thedismissal criteria if the distance of the swipe or flick across thetouchscreen exceeds a threshold distance. In some embodiments, thethreshold distance may be a quarter, half, or ¾ of the length oftouchscreen 504.

Returning to FIG. 7, in some embodiments, in response to detecting amovement of a contact (such as a swipe) on touchscreen 504 whiledisplaying notification 606, device 500 can slide notification 606 onthe touchscreen in the direction of the movement of the contact anddisplay a dismissal indicator 714 adjacent to the notification. As shownin FIG. 7, in some embodiments, the dismissal indicator may be displayedabove the notification, if the direction of the movement of the contactis downwards. The dismissal indicator 714 may provide the user with avisual cue that, if the movement of the contact is continued in the samedirection, the notification will be dismissed. After displaying thedismissal indicator, in some embodiments, if the contact meets thethreshold criteria, then in response to detecting the release of thecontact, device 500 can dismiss notification 606 and remove thedismissal indicator 714 from touchscreen 504. If the contact does notmeet the threshold criteria (for example, if the movement of the contactdoes not exceed a threshold distance), device 500 can display ananimation that slides notification 606 back to its initial position onthe display, and remove the dismissal indicator 714 from the display.Thus, in this example, a user must “push down” the notification farenough to exceed a threshold distance in order to dismiss thenotification; otherwise, the notification rebounds to its originalposition. In some embodiments, as depicted in FIG. 7, dismissingnotification 606 involves displaying an animation that slidesnotification 606 off of touchscreen 504. In some embodiments, theanimation slides notification 606 off of touchscreen 504 in thedirection of the swipe or flick.

As previously discussed, a user may also dismiss a notification bylowering their wrist (as detected by device 500) while the notificationis displayed. In some embodiments, device 500 can respond differentlywhen a notification is dismissed in response to detecting a contact thatmeets the dismissal criteria (as discussed with respect to FIG. 7) thanwhen a notification is dismissed in response to detecting a signalindicative of lowering their wrist, as described earlier. For example,if device 500 is worn on a user's wrist and device 500 detects a signalindicative of the user lowering their wrist, device 500 may assume thatthe user is no longer viewing touchscreen 504, and therefore may turnoff or inactivate touchscreen 504 after dismissing the notification. Incontrast, if device 500 is displaying a notification and detects acontact on touchscreen 504 that meets a dismissal criteria (such as adownward swipe), device 500 may assume that the user is still activelyviewing touchscreen 504, and device 500 may respond to the contact bydismissing the notification and then displaying a clock face, homescreen, or some other screen, such as the screen that was beingdisplayed prior to receiving the alert.

c. Displaying Alert Content

As previously discussed, a received alert includes information, whichmay include a source of the alert, an application associated with thealert, and a time of the alert, along with (possibly) alert content,such as the body of a text message or email, a voicemail message,details regarding a calendar reminder, or other types of content. Anotification representing a received alert may include a first portionof this alert information, such as the alert's source, associatedapplication, or time received.

As previously discussed with respect to FIGS. 6A, 6B, and 7, afterreceiving an alert device 500 can issue a perceptual output, and thendisplay notification 606 in response to detecting a user input within afirst time interval following the perceptual output. After raising theirwrist to view the notification, a user may then wish to view theassociated alert content.

In some embodiments, if device 500 determines that the user continues tomaintain device 500 in the viewing position for a predetermined timeinterval after displaying the notification, device 500 can display someor all of the alert content, which may be referred to as a secondportion of the information. That is, in some embodiments, device 500 canautomatically transition from displaying the notification to displayingthe alert content, if the user holds device 500 in a viewing positionand waits.

FIG. 8 depicts an exemplary sequence of screens that device 500 candisplay in response to receiving an alert. Initially touchscreen 504 maybe dark or inactive. In response to receiving the alert, device 500 canissue a perceptual output. In response to receiving a user input withina predetermined time period after the perceptual output (as describedwith respect to FIG. 6A), device 500 can display notification 606. Inresponse to a determination that the user input continues to be receivedafter a second predetermined time period after displaying notification606—thus indicating that device 500 remains in a viewing position—device500 can display screen 802, which includes notification 606 and alertcontent 804. In some embodiments, device 500 can display screen 802 inresponse to detecting a lack of a second user input within the secondpredetermined time period after displaying notification 606. The seconduser input may be a signal indicative of a user lowering their wrist,for example, and the lack of such an input indicates that the device 500remains in the viewing position.

In this example, the alert content 804 is the body of a text messagerepresented by notification 606. In other examples, the alert contentmay include the subject line and some or all of the body of a receivedemail alert, or may be some or all of the textual content associatedwith a calendar alert, or a multimedia message, for example.

As indicated in FIG. 8, in some embodiments, displaying the alertcontent 804 involves displaying an animation that slides notification606 upwards on touchscreen 504 while sliding the alert content 804 upfrom the bottom of touchscreen 504 for display, so that the notificationand the alert content are displayed on the same screen. In someembodiments, device 500 can slide notification 606 into an upper cornerof touchscreen 504 to provide space for displaying the alert content. Insome embodiments, device 500 can shrink the display size of notification606 to provide space for displaying the alert content.

In some embodiments, if the alert content is too long to be fullydisplayed on touchscreen 504, the alert content can be scrolled. Inresponse to detecting a user input, device 500 can scroll the alertcontent to allow a user to view addition alert content on touchscreen504. Such scroll inputs may include a contact (such as an upward ordownward swipe or flick) on touchscreen 504, for example, or may includea rotation of a rotatable input mechanism, if present. In someembodiments, device 500 can scroll the alert content in accordance withthe user input; for example, in response to an upward swipe ontouchscreen 504, device 500 can move the alert content upwards ontouchscreen 504.

As depicted in FIG. 8, in some embodiments, device 500 can dismiss thenotification and alert content in response to detecting a contact thatmeets a dismissal criteria, as described previously with respect to FIG.7. In some embodiments, dismissing notification 606 and alert content804 involves sliding notification 606 and alert content 804 off oftouchscreen 504. In some embodiments, device 500 can display a dismissalindicator and “rebound” the notification and alert content if themovement of the contact does not exceed a threshold distance, aspreviously described. In some embodiments, device 500 can display aclock face 612 after dismissing the notification and alert content. Insome embodiments, if clock face 612 is displayed after alert content isdismissed, the clock face may be displayed without an indication of anunread alert, since the alert content has been displayed.

As previously discussed, device 500 can display alert content inresponse to detecting that device has been maintained in the viewingposition after displaying a notification. However, in some cases, a usermay not wish to wait to view the alert content by maintaining device 500in the viewing position for the predetermined time interval. Thus, insome embodiments, device 500 can also display screen 802 in response toa detecting contact with touchscreen 504 while notification 606 isdisplayed. In some embodiments, the contact for invoking display of thealert content 804 may comprise a movement of the contact on touchscreen504, such as a swipe or flick. In some embodiments, the swipe or flickmust be in the same direction as the animation that slides notification606 onto touchscreen 504, such as an upward swipe on touchscreen 504,thus conceptually “pulling up” more alert information after thenotification. In some embodiments, the contact can be a touch (e.g., afinger tap) on or near notification 606.

As depicted in FIG. 24, in some embodiments, in response to receiving analert while touchscreen 504 is actively displaying content, device 500can display a notification banner 2402 across the top of touchscreen 504while still displaying at least a portion of the screen content. In someembodiments, in response to receiving an alert while touchscreen 504 isactively displaying content, device 500 may also issue a perceptualoutput 702. In the example shown in FIG. 24, the content displayed ishome screen 706. In response to detecting a contact on notificationbanner 2402, such as a swipe or tap, device 500 can display screen 802with alert content 804.

Some alerts may not have any alert content. For example, a clock alarm,low-battery alert, or fitness alert may not have any alert content.Thus, in some embodiments, device 500 can continue to display anotification without transitioning to displaying the alert content.

d. Suppressing Automatic Display of Alert Content

In some cases, a user may not want device 500 to automatically displayalert content as described with respect to FIG. 8, due to privacyconcerns or for other reasons. Thus, in some embodiments, device 500 canprovide an option for a user to suppress such automatic display of alertcontent by changing configuration data stored on device 500. In someembodiments, before transitioning to the display of the alert content,device 500 can obtain the configuration data to determine whether thealert content should be displayed. If the configuration data indicatesthat the alert content should be displayed, device 500 can display thealert content as previously described with respect to FIG. 8. If theconfiguration data indicates that the alert content should not bedisplayed, device 500 can continue to display the notification, withouttransitioning to the alert content.

In some embodiments, if device 500 is configured to suppress automaticdisplay of the alert content (via the configuration data), device 100may still display the alert content in response to detecting a contact,such as a tap or swipe, on a displayed notification.

e. Alerts Comprising Audio Content

Some received alerts may comprise audio content. Such alerts may includevoicemail, audio, or “push to talk” messages. In some embodiments, asdepicted in FIG. 9, the displayed alert content can include a playbackaffordance 902 for playing back the audio content. In response todetecting a selection of playback affordance 902, device 500 can playthe audio content. In some embodiments, if the audio content is receivedas part of a live audio conversation (such as if the device is operatingin the “push to talk” mode) and the user selects the playbackaffordance, device 500 can play the initial audio message in response tothe selection of the affordance, and device 500 can play subsequentaudio messages live, as they are received, without requiring subsequentselections of the affordance.

f. Text Message Alerts

In some embodiments, if the alert is a text message, a user may wish toview a text message conversation associated with the alert. FIG. 10depicts a sequence of screens that device 500 can display afterreceiving a text message alert. This sequence is similar to the sequenceshown in FIG. 8, and depicts displaying notification 606 and alertcontent 804 corresponding to a text message received from sender JasonJones. However, in this example, while displaying screen 802, device 500detects a contact on touchscreen 504. The contact may be a touch or tapon touchscreen 504 at a location corresponding to application affordance608, for example, or a horizontal swipe on touchscreen 504. In responseto detecting the contact with touchscreen 504, device 500 can displayscreen 1002.

Screen 1002 includes some or all of a text message conversation betweenthe user and the source of the text message alert. In this example, thetext message conversation includes text messages sent to and receivedfrom Jason Jones. In some embodiments, the text messages in the textmessage conversation are arranged chronologically based on the order inwhich they were received or sent.

g. Response Options

In some cases, upon viewing a notification or alert content, a user maywish to respond to the alert. Because device 500 is a reduced-sizedevice with a relatively small touchscreen, user interfaces that may beused to respond to alerts on larger devices, such as cellular phones,may be ineffective and/or awkward on touchscreen 504. A user may wish tobe able to respond to an alert without needing to provide a sequence ofrelatively accurate touchscreen inputs, which may be difficult orfrustrating on a reduced-size device. Thus, in some embodiments, device500 can provide user interfaces that enable the user to respond toalerts more quickly and easily on a reduced-size screen.

As previously described, device 500 can scroll alert content in responseto detecting a contact on touchscreen 504 or, in some embodiments, inresponse to a rotation of a rotatable input mechanism. In someembodiments, if a user attempts to scroll beyond the bottom of the alertcontent (the end of the content), device 500 can respond by displayinguser interface objects that are associated with actions that may beperformed by an application associated with the alert.

For example, FIG. 11 depicts a sequence of screens that device 500 candisplay in response to receiving an alert. These screens are similar tothose described with respect to FIG. 4. While displaying the bottom ofthe alert content 804 (in this case, the alert content is a textmessage), device 500 detects a user input requesting to scroll beyondthe bottom of the alert content; that is, a user input requesting tomove the alert content upwards to display more alert content. The userinput may be an upward swipe on touchscreen 504, for example, or arotation of a rotatable input mechanism. In response to detecting theuser input, device 500 can scroll the notification 606 and alert content804 upwards and scroll user interface objects 1112, 1114 ontotouchscreen 504 below the alert content. In this example, thenotification 606 is scrolled off of the top of touchscreen 504 and is nolonger displayed.

In the example of FIG. 11, the alert is a text message. Thus, in thisembodiment, the user interface objects 1112, 1114 scrolled ontotouchscreen 504 are associated with actions corresponding to a textmessage application. In particular, user interface object 1112 isassociated with a reply action, and user interface object 1114 isassociated with a dismiss action. For other types of alerts, the userinterface objects scrolled onto touchscreen 504 may be different. Forexample, for a calendar invitation, the actions may include accept ordecline. For a voicemail alert, actions may include call back or sendmessage. In some embodiments, there may be more than two displayed userinterface objects.

In some embodiments, in response to detecting a selection of userinterface object 1114, which is associated with a dismiss action, device500 can dismiss the alert as previously described with respect to FIG.8.

In some embodiments, in response to detecting a selection of userinterface object 1112, which is associated with a reply action, device500 can display screen 1120. Screen 1120 includes several user interfaceobjects 1122, 1124, 1126, 1128 that correspond to options for replyingto the text message. In this example, the reply options include “smartreply,” “emoji,” “dictate,” and “KB” (keyboard). Such reply options mayinclude functionality as described in U.S. Provisional PatentApplication Ser. No. 62/044,923 “Historical Buttons for Input Methods,”filed Sep. 2, 2014, and naming Nicholas Zambetti as inventor; U.S.Provisional Patent Application Ser. No. 62/127,800 “Historical Buttonsfor Input Methods,” filed Mar. 3, 2015, and naming Nicholas Zambetti asinventor; U.S. Provisional Patent Application Ser. No. 62/129,903“Historical Buttons for Input Methods,” filed Mar. 8, 2015, and namingNicholas Zambetti as inventor. These applications are incorporated byreference in their entirety.

In response to detecting a selection of user interface object 1122,corresponding to “Smart Reply,” device 500 can display smart replyscreen 1130. Smart reply screen 1130 includes a user interface forselecting a predefined response message 1132, 1134, 1136. In someembodiments, the content of the predefined response messages may beprovided as a default by device 500, or may be customized by the user.In some embodiments, the content of the predefined response messages maybe received by device 500 from an external device.

In response to detecting a selection of a predefined response message1132, 1134, 1136, device 500 can send the predefined response message tothe alert source, and display message-sent confirmation screen 1140.After displaying message-sent confirmation screen 1140 for apredetermined time interval, device 500 can display clock face 212 or ahome screen. In this example, clock face 212 does not include anindication of an unread alert corresponding to the received alertbecause the alert content has been displayed.

Returning to screen 1120, if device 500 detects a selection of userinterface object 1124 instead of 1122, device 500 can display a userinterface for selecting an emoji (e.g., ideogram, clip art, oranimation) to send as a reply to the alert source. In response todetecting a selection of an emoji, device 500 can send the selectedemoji to the source of the alert and display message-sent confirmationscreen 1140.

In some embodiments, instead of sending a predefined response or emojiimmediately after selection, device 500 can display a confirmationaffordance. In response to detecting a selection of the confirmationaffordance, device 500 can send the predefined response or emoji asdescribed above.

In some embodiments, in response to detecting a selection of userinterface object 1126, device 500 can record an audio input from amicrophone on device 500, and send data corresponding to the recordedaudio as a reply to the source. In some embodiments, the recorded audiomay be sent as audio message data. In other embodiments, the recordedaudio may be transcribed by device 500 and sent as transcription data.In some embodiments, instead of immediately sending the datarepresenting the audio recording to the source, device 500 can displayan indication of the recorded audio on touchscreen 504, along with asend affordance which, when selected, causes device 100 to send the datacorresponding to the audio to the source.

In some embodiments, in response to detecting a selection of userinterface object 1128, device 500 can display a virtual keyboard toenable a user to type a response to the alert.

As depicted in FIG. 12A, in some embodiments, after scrolling up userinterface objects 1112, 1114 onto touchscreen 504, in response todetecting a user input requesting to scroll past the bottom of userinterface object 1114, device 500 can scroll user interface objects1202, 1204, 1206, and 1208 representing reply options onto touchscreen504 below user interface objects 1112, 1114. These reply options includetwo predefined response messages 1202, 1204 and the dictate 1208 andemoji 1206 options previously described with respect to FIG. 11. Inresponse to detecting a selection of one of the reply options 1202,1204, 1206, 1208, device 500 can respond as described with respect toFIG. 11.

As depicted in FIG. 12B, in some embodiments, instead of scrolling upuser interface objects 1112, 1114 below the bottom of the alert content,device 500 can scroll user interface objects 1202, 1204, 1206, and 1208onto the screen below the bottom of the alert content. In this example,in response to detecting a user input requesting to scroll past thebottom of the alert content 804 (such as an upward swipe), device 500scrolls these reply options onto touchscreen 504 under the bottom of thealert content.

FIG. 12C illustrates an exemplary animation that may be displayed bydevice 500 as part of an interface for using “Smart Replies,” asdescribed above in reference to FIGS. 11-12B. On screen 1210, device 500displays an alert (e.g., text message 1212) and user interface object1214, which is associated with a reply action. In response to receivinguser input associated with the reply action (e.g., a touch ontouchscreen 504 at the location of user interface object 1214), device500 may display an animated reveal of a plurality of predefined responsemessages. For example, as shown in FIG. 12C, screen 1220 initiallydisplays user interface objects 1222 and 1224 corresponding topredefined response messages. User interface objects 1222 and 1224 areanimated to appear at the bottom of screen 1220 and translate on-screenin an upward direction, as indicated by arrow 1226. Over the course ofthe animated reveal, user interface objects 1222 and 1224 translate tothe top of screen 504 as user interface objects 1228, 1230, and 1232appear below on screen 1220. User interface object 1228 indicates athird predefined response message, while user interface object 1230indicates an emoji response, and user interface object 1232 indicates adictation response.

The user may provide a user input indicating a selection of apredetermined response message or other response option (e.g., emoji ordictation). For example, the user may provide a touch on touchscreen 504at the location of user interface object 1228. In response to detectingthe user input indicating a selection of the predetermined responsemessage or other response option, device 500 may remove the display ofthe other predetermined response messages and response options (e.g.,those not selected by the user). As shown in FIG. 12C, in response toreceiving a user input indicating a selection of the “Not sure”predetermined response message (e.g., user interface object 1228),device 500 removes the display of user interface objects 1222, 1224,1230, and 1232. Subsequently, device 500 may animate the selectedpredetermined response message to pause briefly, then translate off ofscreen 1220 and disappear, as indicated by arrow 1234. After pause,translation, and removal of the displayed predetermined responsemessage/other response option, device 500 may display a second userinterface screen (e.g., screen 1240), such as clock face 212 or a homescreen. For example, after user interface object 1224 translates off ofscreen 1220, device 500 may reveal screen 1240 by fading in,transitioning from out-of-focus to in-focus, and so forth. Device 500may also send the selected predetermined response message to the alertsource.

Device 500 can display other response options to enable a user torespond to other types of alerts. For example, FIGS. 13A-B showexemplary sequences of screens that device 500 can display ontouchscreen 504 to enable a user to respond to a clock alarm alert orsocial media “friend request” alert. In the example shown in FIG. 13A,device 500 receives a clock alarm alert and issues a perceptual output.In response to detecting a user input within a predetermined timeinterval after the perceptual output, device 500 displays screen 1302that includes notification 1304 corresponding to the clock alarm alert.In response to detecting a contact on notification 1304, device 500displays response screen 1330. The contact may be an upward swipe ontouchscreen 504 while notification 1304 is displayed. In response tothis contact, device 500 displays screen 1330. In this case, theresponse options include “snooze” 1306 and “dismiss” 1308.

In the example shown in FIG. 13B, device 500 receives a “friend request”alert from a social media application and issues a perceptual output. Inresponse to detecting a user input within a predetermined time intervalafter the perceptual output, device 500 displays screen 1310 thatincludes notification 1312 corresponding to the friend request alert. Inresponse to detecting a contact with touchscreen 504 while displayingscreen 1310, device 500 displays response screen 1340. The contact maybe an upward swipe on touchscreen 504, for example. In response todetecting this contact, device 500 displays screen 1340. In this case,the alert response options include “accept” 1314 and “deny” 1316 toallow a user to accept or deny the friend request.

A person of skill in the art will recognize that many other responseoptions are possible for other types of alerts.

It should be noted that, in the previous examples shown in FIGS. 8-11,in response to an upward swipe on touchscreen 504 while displaying anotification, device 500 displays alert content associated with thereceived alert. However, in the examples shown in FIGS. 13A-B, thereceived alerts do not have associated alert content. In someembodiments, if a received alert does not have alert content, device 500can respond to a contact (such as an upward swipe or tap) on touchscreen504 while displaying a notification by displaying response optionsrather than by displaying alert content.

As discussed earlier, in some embodiments, device 500 can detect theintensity of contacts on touchscreen 504 (e.g., using intensity sensor524). Device 500 can then respond to contacts on touchscreen 504 basedon the intensity of the contact. Returning briefly to FIG. 11, in someembodiments, while displaying alert content 804, in response todetecting a contact with touchscreen 504 that has a characteristicintensity that is above a threshold intensity, device 500 can displaysome or all of user interface objects 1122, 1124, 1126, and 1128.

In some embodiments, a user may access user interface objects 1122,1124, 1126, and/or 1128 either by scrolling beyond the bottom of alertcontent, as described earlier, or by touching touchscreen 504 with acharacteristic intensity that is above a threshold intensity (e.g., ahard press on touchscreen 504, detected by, e.g., intensity sensor 524).

FIG. 14 depicts another sequence of screens that may be displayed bydevice 500 to enable a user to respond to a received alert. In thisexample, while displaying the alert content 804, device 500 detects acontact with touchscreen 504 that has a characteristic intensity that isabove a threshold intensity. In response to detecting the contact with acharacteristic intensity above the threshold, device 500 can displayresponse screen 1402.

Response screen 1402 includes four user interface objects 1404, 1406,1408, 1414 corresponding to four response options. In response todetecting an input indicating selection of user interface object 1404,device 500 can display screen 1120, as shown and described with respectto FIG. 11.

In response to detecting a selection of user interface object 1406,device 500 can dismiss the alert and display a clock face or homescreen.

In response to detecting a selection of user interface object 1408,device 500 can suppress subsequent alerts indefinitely or for apredetermined period of time (e.g., by not causing a perceptual outputin response to receiving an alert, and/or by not displaying any newnotifications).

In some embodiments, in response to detecting a selection of userinterface object 1410, device 500 can launch an application associatedwith the received alert and view the alert in the application. Launchingan application may correspond to executing the application in theforeground of device 500 and/or displaying the application ontouchscreen 504. In this example, since the alert is a text message,device 500 can launch a text message application. In other examples,depending on the received alert the launched application may be an emailapplication, a calendar application, a weather application, a socialnetwork application, or some other type of application. After launchingan application, in response to detecting a depression of a hardwarebutton or a depression of a rotatable, depressible mechanism (if eitheror both are present on device 500, as depicted in FIG. 5A), device canexit the application and display the home screen.

In the example shown in FIG. 14, response screen 1402 includes userinterface objects 1404, 1406, 1408, 1410 that are appropriate forresponding to a text message or email alert. However, as previouslydiscussed with respect to FIGS. 12A-B, the response screen can havedifferent user interface objects that are appropriate for responding todifferent types of alerts. For example, if the alert is a clock alarm,then instead of the “reply” option 1404, the response screen may providea “snooze” option. As another example, if the alert is an audio message,the response screen may provide a “play” option to allow the user toplay the audio message. In some embodiments, the response screen mayprovide an “open in phone” option. In response to detecting a selectionof the “open in phone” option, device 500 can send data to an externalelectronic device that is in communication with device 500, such as acellular phone, to cause the external electronic device to launch theapplication associated with the alert.

It should be noted that the response interfaces described with respectto FIGS. 13A-B and FIG. 14 are not part of the associated application,which may or may not be executing on device 500; instead, the responseinterfaces are part of an alert user interface. In some embodiments, athird party may supply response options for an application executing onan external electronic device that is in communication with device 500.

2. Managing Multiple Alerts

In some embodiments, device 500 may receive multiple alerts and displaymultiple consecutive notifications.

FIG. 15 depicts a sequence of screens that may be displayed by device500 in response to receiving multiple alerts. As in previous examples,initially, touchscreen 504 may be dark or inactive. In response toreceiving a first alert, device 500 issues a first perceptual output602. In response to receiving a user input within a first time intervalfollowing the first perceptual output 602, device 500 displays firstnotification 606, as previously shown and described with respect to FIG.6A.

While displaying the first notification, device 500 receives a secondalert. In response to receiving the second alert, device 500 replacesscreen 604 with screen 1502. In some embodiments, in response toreceiving the second alert, device 500 may also issue a secondperceptual output 1506. Screen 1502 includes a second notification 1504representing the second received alert. In this example, the secondreceived alert is an email from sender Julia Smith. The secondnotification may be animated onto the screen in a manner similar to thatdescribed earlier with respect to FIG. 8.

Device 500 can dismiss second notification 1504 in response to detectinga user input meeting a dismissal criteria, as previously discussed withrespect to FIG. 8. After dismissing the second notification, device 500may display a home screen 706 or a clock face 612. As depicted in FIG.15, the home screen or clock face may include an indication of twounread alerts corresponding to the first and second alerts. Note thatthe indicator of unread alerts 614 depicted on the clock face 612 inFIG. 15 is larger than the indicator of an unread alert depicted on theclock face 612 in FIG. 6B. As will be discussed in more detail below, insome embodiments, the size of the indicator may provide an indication ofthe number of unread alerts.

FIG. 16 depicts another exemplary sequence of screens that can bedisplayed by device 500 in response to receiving multiple alerts. Inthis example, device 500 receives a first alert, issues a firstperceptual output 602, and displays a first notification 606 and firstalert content 804 in response to various user inputs, as previouslydescribed with respect to FIG. 8.

While displaying first alert content 804, device 500 then receives asecond alert including information. In response to receiving the secondalert, device 500 can display screen 1502 with second notification 1504as described with respect to FIG. 15. In some embodiments, in responseto receiving the second alert, device 500 may issue a second perceptualoutput 1506. Device 500 can dismiss second notification 1504 in responseto user inputs that meet a dismissal criteria, as previously describedwith respect to FIG. 8. After dismissing second notification 1504,device 500 can display clock face 612 or home screen 706, as previouslydescribed with respect to FIG. 15. In some embodiments, instead ofdisplaying clock face 612 or home screen 706, device 500 can re-displayfirst alert content 804 after dismissing second notification 1504.

FIG. 17 depicts another sequence of screens device 500 can display. Thissequence is similar to the sequence depicted in FIG. 16, but instead ofdismissing second notification 1504, the user wishes to view the secondalert content. Device 500 can display the second alert content 1712 inresponse to detecting a user input while displaying the secondnotification 1504, as previously described with respect to FIG. 8. Inthis example, second alert content 1712 includes a subject line 1710 forthe email alert. The user input may be an upward swipe or tap on thesecond notification, for example.

In the example depicted in FIG. 17, after viewing the second alertcontent 1712, the user wishes to invoke the application associated withthe second alert. In some embodiments, in response to detecting acontact on touchscreen 504 at a location corresponding to the secondalert content or the second alert notification, device 500 can launch anapplication associated with the second alert and display screen 1714. Insome embodiments, in response to detecting a selection of applicationaffordance 1708, device 500 can launch an application associated withthe second alert and displays screen 1714.

In this example, the application associated with the second alert is anemail application. Thus, in response to detecting a selection ofapplication affordance 1708, device 500 can launch an email application.In some embodiments, when device 500 launches an application associatedwith an alert in this manner, the alert is opened within theapplication, as depicted in screen 1714.

After launching and viewing an application, a user may wish to return tothe home screen. In response to detecting a depression of input button506, which may be a depressible hardware button or a depressible,rotatable input mechanism, device 500 can display home screen 706. Inthis example, home screen 706 is displayed without an indication ofunread alerts corresponding to the first alert and the second alert,because the first alert content 804 and second alert content 1712 haveboth been displayed.

FIGS. 18-20 depict additional screen sequences that device 500 candisplay in response to receiving multiple alerts and detecting inputs aspreviously described.

In the sequence depicted in FIG. 18, device 500 receives a first alertand displays a first notification, as shown and described with respectto FIG. 17. Device 500 receives a second alert while displaying thefirst notification. In response to receiving the second alert, device500 displays a second notification. In this example, the user dismissesthe second notification as previously described with respect to FIG. 16.After dismissing the second notification, device 500 re-displays thefirst notification. The user then dismisses the first notification, anddevice 500 displays a home screen. In this example, the home screen isdisplayed with an indication of two unread alerts corresponding to thefirst and second alerts.

FIG. 19 is similar to FIG. 18. However, in this example, after device500 displays the first notification, the user holds device 500 in theviewing position, and device 500 responds by displaying the first alertcontent, as previously described with respect to FIG. 18. Whiledisplaying the first alert content, device 500 receives a second alertand displays a second notification. The user dismisses the secondnotification, and device 500 then re-displays the first alert content.The user dismisses the first alert content, and device 500 displays homescreen 706. In this example, the home screen is displayed with anindication of one unread alert corresponding to the second alert.

FIG. 20 is similar to FIG. 15. However, instead of dismissing the secondnotification, the user taps the application affordance 2002 to launchthe application associated with the second alert. In response todetecting a selection of application affordance 2002, device 500launches the application and displays the second alert content withinthe application. The user then exits the application and returns to thehome screen 706 by depressing the hardware button or depressible,rotatable input mechanism 506.

Device 500 may display other user interfaces for viewing multiplenotifications or alerts. As depicted in FIG. 21, in some embodiments, inresponse to detecting a contact on a notification 606 representing afirst alert, device 500 can display screen 2102 comprising a first pane2104 with a portion of the alert content 2106 associated withnotification 606, and a portion of one or more additional panes 2108indicating other alert content for other received alerts. In someembodiments, screen 2102 may include paging dots 2110 that provide theuser with an indication of the number of other panes that may bedisplayed, and the position of the currently displayed pane. In responseto detecting a flick or swipe on touchscreen 504, device 500 can scrollthe panes to display alert content for other received alerts.

In some embodiments, in response to detecting a contact on a pane 2104,device 500 can display screen 2114 comprising the full alert content2120 associated with notification 606. In some embodiments, screen 2114further comprises paging dots 2118 that may provide the user with anindication of other messages that may be displayed, such as othermessages in a text message conversation. In some embodiments, the colorof the paging dots 2118 on screen 2114 may indicate a type of message.For example, the paging dot associated with pane 2116 containing thecurrent alert content 2120 may be one color, while other messages, suchas reply messages, may be indicated by paging dots of different colors.

3. Muting Notifications

In some cases, after receiving an alert from a source, a user may wishto suppress subsequent perceptual outputs for alerts from the samesource, and/or suppress display of notifications representing alertsfrom the same source. That is, a user may not wish to be notified by aperceptual output if subsequent alerts are received from the samesource, and/or may not wish to have the associated notificationdisplayed on touchscreen 504. As depicted in FIG. 22, device 500 canreceive an alert from a source and display a notification 606. In thisexample, while displaying the notification, device 500 detects a contactwith touchscreen 504 that has a characteristic intensity that is above athreshold intensity. In response to detecting the contact with acharacteristic intensity above the threshold intensity, device 500 candisplay a mute affordance 2204 for muting subsequent alerts receivedfrom the same source, or alerts that are associated with the sameapplication. In response to detecting a selection of the mute affordance2204, device 500 can suppress perceptual outputs and notifications foralerts received from the same source or application indefinitely or fora predetermined period of time.

4. Grouped Notifications

In some cases, device 500 may receive multiple alerts simultaneously orwithin a brief time period. This may happen, for example, if device 500has been turned off for a period of time. When device 500 issubsequently turned on, it may receive all of the alerts that wouldotherwise have been received if device 500 had not been turned off. Inthis case, a user may be annoyed by having to view and dismiss multipleconsecutive notifications.

Thus, in some embodiments, in response to receiving multiple alerts,device 500 may display a single grouped notification representingmultiple alerts rather than displaying a single notification for eachreceived alert. Device 500 may determine whether to display a groupednotification representing multiple alerts based on grouping criteria.For example, device 500 may group alerts for representation by a singlenotification based on whether they are received within a predeterminedtime interval, whether they are received from the same source, whetherthey are associated with the same application, or some combination ofthese criteria. In some embodiments, device 500 can excludetime-sensitive alerts from being included in grouped notifications, andinstead display a single notification for each time-sensitive alert.Such time-sensitive alerts may include system alerts (such as batteryalerts) or urgent calendar reminders, for example.

FIGS. 23A-C depict examples of grouped notifications 2302, 2304, 2306that represent multiple alerts. As depicted in FIGS. 23A-C, in someembodiments, device 500 can respond differently to user inputs whendisplaying a grouped notification than when displaying a notificationrepresenting a single alert. For example, as previously described withrespect to FIG. 8, in response to detecting a contact on a notificationrepresenting a single alert (such as an upward swipe), device 500 maydisplay the alert content. In contrast, in response to detecting acontact on a group notification representing multiple alerts, device 500may display an inbox for an application associated with the multiplealerts (if the alerts are all associated with a single application, andthe application has an inbox), or may display a list of notificationsthat includes separate notifications for each of the received alertsthat were represented by the grouped alert. FIGS. 23A-C depict examplesof grouped notification screens and responses to user inputs.

In the exemplary screen sequence depicted in FIG. 23A, device 500receives three text messages from the same source, Jason Jones, anddisplays a grouped notification 2302 representing the text messages. Inresponse to detecting a contact on the grouped notification, device 500can display a text message inbox 2308 for Jason Jones, with a list ofthe received messages. The contact may be a tap or swipe, for example.In response to detecting a selection of one of the messages in the list,device 500 can display the associated alert content.

In the exemplary screen sequence depicted in FIG. 23B, device 500receives two alerts from two different sources, Chris Black and JasonJones. The alerts are both associated with the same application. In thisexample, the application is a text message application. In response toreceiving the two alerts, device 500 can display a grouped notification2304 representing the two alerts. In response to detecting a contact onthe grouped notification 2304, device 500 can display a text messageinbox 2310 listing the two messages. In response to detecting aselection of one of the messages in the list, device 500 can display theassociated alert content.

In still another example, as depicted in FIG. 23C, device 500 receivesmultiple alerts associated with multiple applications. Device 500 candisplay a grouped notification 2306 representing the multiple alerts. Inresponse to detecting a contact on the grouped notification 2306, device500 can display a list of notifications 2312 that includes separatenotifications for each of the received alerts that were represented bythe grouped notification. In response to detecting a selection of one ofthe notifications, device 500 can display the associated alert content.

In some embodiments, in response to receiving multiple alerts that meetgrouping criteria, device 500 can issue multiple perceptual outputs. Insome embodiments, in response to receiving multiple alerts that meet thegrouping criteria, device 500 can issue a single perceptual outputrather than issuing a perceptual output for each alert.

5. Indication of Unread Alerts

As previously discussed with respect to FIGS. 6B, 7, and 15, in someexamples, a displayed clock face or home screen can include a userinterface object that provides an indication of unread alerts. Unreadalerts may correspond to alerts that have been received but not viewedby the user, or may correspond to alerts that have been marked as“unread” by the user. Device 500 may determine whether an alert has beenviewed based on whether some or all of the alert content has beendisplayed on touchscreen 504, how long the alert content was displayedon touchscreen 504, whether any audio content associated with the alerthas been played, and/or whether the alert content was displayedautomatically (e.g., in response to a signal indicative of a userraising their wrist) or in response to a contact with touchscreen 504,for example. In some embodiments, if an alert does not include any alertcontent (e.g., a clock alarm), then device 500 may consider the alert asread if a notification representing the alert has been displayed.

In some embodiments, device 500 may receive an alert that generates atransient notification. Such a notification may only be useful to a userfor a relatively brief period. For example, if a user is exercising andachieves a fitness milestone (such as being halfway through a workout),device 500 may receive such a transient alert notifying the user of themilestone. In this case, if the user raises their wrist within thepredetermined time interval after device 500 issues the perceptualoutput for the transient alert, device 500 can display a notificationrepresenting the alert. However, if the user raises their wrist sometime later, device 500 may display a clock face or home screen, and theclock face or home screen may not include an indication of an unreadalert corresponding to the alert because the alert may no longer berelevant to the user.

Returning to FIG. 7, in exemplary home screen 706, user interface object708 provides an indication of unread alerts by displaying the number ofunread alerts. In other examples, a user interface object may provide anindication of unread alerts in a different manner, such as by displayinga colored banner where the color provides an indication of the number ofunread alerts (e.g., a darker banner indicates more unread alerts). Insome embodiments, a user interface object may provide an indication thatthere are unread alerts without providing any indication of the numberof unread alerts.

In some embodiments, as depicted in FIGS. 6B, 6C, and 15, device 500 canprovide an indication of an unread alert(s) by displaying a dot,chevron, or other shape, such as indication 614. In some embodiments,the color of the dot, chevron, or other shape may indicate the presenceof unread alerts; for example, a red shape may indicate that there areunread alerts, while a green shape may indicate that there are no unreadalerts. In some embodiments, the shape may blink, flash, or fluctuate insize with a frequency that is indicative of the number of unread alerts.For example, a higher blink frequency may indicate more unread alerts.In some embodiments, the size of the shape can provide an indication ofthe number of unread alerts. A small shape, for example, may indicate asingle unread alert (as in FIG. 6B), while a larger shape may indicatemore unread alerts (as in FIG. 15). A person of skill in the art willappreciate that these approaches to indicating the number of unreadalerts may be combined in many different ways.

In some embodiments, the display of the shape includes an effect. Forexample, the shape may fade in or slide into position on touchscreen 504(e.g., slide in from the top edge of the screen). Optionally, the effectis animated. In some embodiments, the effect is performed in response toa user input (e.g., a user raising his or her wrist).

In some embodiments, the display of the shape is removed according toremoval criteria. For example, the shape may be removed after it hasbeen displayed for a predetermined period of time or in response to auser input (e.g., the user lowering his or her wrist). In someembodiments, the removal of the shape includes an effect. For example,the shape may fade out or slide off of touchscreen 504 (e.g., slide offthe top edge of the screen). Optionally, the removal of the shape isanimated.

The features and/or effects associated with the indication of an unreadalert described above may indicate to a user that there is an unreadalert. For example, animation of the appearance or fluctuation in sizeof the indication may draw the user's attention to the fact that thereis an unread alert.

Furthermore, some shapes may provide additional technical effects. Insome embodiments, an arrow, a triangle, a chevron (e.g., 614 in FIG.6C), or other graphical object that provides a directional indicationmay provide a user with a visual cue that an input will cause device 500to perform an operation associated with an unread alert. For example, agraphical object that provides an indication of direction, such aschevron 614 depicted in FIG. 6C, may indicate to a user that a swipe,drag, or flick on touchscreen 504 in the direction that the object isindicating (e.g., downward in the case of chevron 614 in FIG. 6C) willcause device 500 to perform an action associated with the unread alert.In one embodiment, a swipe in the direction that the directional objectis pointing causes device 500 to display the content of the unread alertsuch as, for example, alert content 804 on screen 802 in FIG. 8. Inanother embodiment, a swipe in the direction indicated by the objectcauses device 500 to display a notification of the alert such as, forexample, notification 606 in FIG. 6A. In yet another embodiment, a swipein the direction indicated by the object causes device 500 to display alist of one or more notifications, which may include a notification ofthe unread alert, or launch an application that corresponds to theunread alert. For example, device 500 may display multiple notificationsor launch an application that corresponds to the unread alert asdescribed in co-pending U.S. Provisional Patent Application Ser. No.62/044,953, “Reduced-size Notification Interface,” filed Sep. 2, 2014,the content of which is hereby incorporated by reference.

A person of skill in the art will appreciate that various positions andorientations of the shape or object indicating an unread alert arepossible. For example, an indication at the bottom of touchscreen 504may include an upward pointing arrow, triangle, chevron, or othergraphical object that provides an upward directional indication toindicate that there is an unread alert and that an upward swipe ontouchscreen 504 will cause device 500 to display the content of theunread alert, a notification of the alert, a list of notifications, oranother display associated with alerts and/or notifications.

6. Interacting with a Reminder of an Event

In some embodiments, an alert is associated with an event (e.g., aparty, meeting, game, etc.). The alert content may include informationassociated with the event, such as the date, time, and location of theevent. In some embodiments, a reminder of an event is displayed based onan estimate of the amount of time it will take for the user to get tothe event. The estimated amount of time optionally depends on a locationof the user and a location associated with the event. The amount of timemay be, for example, the estimated walking, biking, publictransportation, or driving time generated by a map application,navigation application, or the like. In some embodiments, the reminderis displayed before the time of the event by the estimated amount oftime it will take the user to get to the event. In some embodiments, thereminder is displayed before the time of the event by the estimatedamount of time it will take the user to get to the event plus apredetermined amount of time to give the user time to prepare to leavefor the event in order to arrive on time.

In some embodiments, the notification or reminder of an event includesan affordance. In response to detecting a selection of the affordance,device 500 may activate a messaging application that prepares a messageaddressed to a person associated with the event (e.g., the organizer ofthe event or the person that invited the user to the event). In thisway, the user may easily provide the person associated with the event anupdate of the user's status (e.g., “I haven't left yet. I'll be there in10 minutes.”). In some embodiments, in response to detecting a selectionof the affordance associated with a notification or reminder of anevent, device 500 may activate a map application, navigationapplication, or the like, that provides or displays directions to theevent. The directions may include directions from the current locationof the user to a location associated with the event.

7. Processes for Managing Notifications and Alerts

FIG. 25 is a flow diagram illustrating process 2500 for managingnotifications and alerts. Process 2500 may be performed at an electronicdevice with a touch-sensitive display screen, such as device 500 (FIG.5A). At block 2502, the device receives an alert comprising information.At block 2504, in response to receiving the alert, the device issues aperceptual output (e.g., using haptic mechanism 542). At block 2506, thedevice detects a user input. At block 2508, in response to detecting theuser input, the device determines whether the user input was detectedwithin a predetermined time interval following the perceptual output. Inaccordance with a determination that the user input was received withinthe predetermined time interval, at block 2510, the device displays anotification comprising a first portion of the information (e.g., on.Optionally, the device determines whether the user input continues to bedetected after a second predetermined time interval after displaying thenotification. In accordance with a determination that the user inputcontinues to be detected, the device displays a second portion of theinformation, where the second portion is different from the firstportion.

Note that details of the processes described above with respect toprocess 2500 (e.g., FIGS. 25 and 6A-8) are also applicable in ananalogous manner to the other processes described herein. For example,processes 2600 and 2700 may include one or more of the characteristicsof the various processes described above with reference to process 2500.For brevity, these details are not repeated in the descriptions of theother processes. The various methods and techniques described above withreference to method 2500 may be optionally implemented as one or morehardware units, such as those described with regard to FIG. 5B.

FIG. 26 is a flow diagram illustrating process 2600 for managingnotifications and alerts. Process 2600 may be performed at an electronicdevice with a touch-sensitive display screen, such as device 500 (FIG.5A). At block 2602, the device receives a plurality of alerts. At block2604, in response to receiving the alerts, device 500 determines whetherthe plurality of alerts meets a grouping criteria. At block 2606, thedevice detects a user input. At block 2608, in accordance with adetermination that the plurality of alerts meets the grouping criteria,and in response to detecting the user input, the device displays agrouped notification representing the plurality of alerts. In accordancewith a determination that the plurality of alerts does not meet thegrouping criteria, and in response to detecting the user input, at block2610, the device displays a plurality of notifications representing theplurality of alerts. Optionally, the grouping criteria is based onwhether the plurality of alerts are received from the same source;whether the plurality of alerts exceeds a numeric threshold of alerts;whether the plurality of alerts are associated with the sameapplication; and/or whether the plurality of alerts are received withina predetermined time interval.

Note that details of the processes described above with respect toprocess 2600 (e.g., FIGS. 26 and 23) are also applicable in an analogousmanner to the other processes described herein. For example, processes2500 and 2700 may include one or more of the characteristics of thevarious processes described above with reference to process 2600. Forbrevity, these details are not repeated in the descriptions of the otherprocesses. The various methods and techniques described above withreference to method 2600 may be optionally implemented as one or morehardware units, such as those described with regard to FIG. 5B.

FIG. 27 is a flow diagram illustrating process 2700 for managingnotifications and alerts. Process 2700 may be performed at an electronicdevice with a touch-sensitive display screen, such as device 500 (FIG.5A). At block 2702, while displaying content, the device receives analert comprising information. At block 2704, in response to receivingthe alert, device 500 displays a notification banner across the display.The banner comprises a portion of the information. At least a portion ofthe content continues to be displayed on the display. At block 2706, thedevice detects a contact on the banner. In response to detecting thecontact, at block 2708, the device displays a second portion of theinformation. The second portion is different from the first portion.

Note that details of the processes described above with respect toprocess 2700 (e.g., FIGS. 27 and 24) are also applicable in an analogousmanner to the other processes described herein. For example, processes2500 and 2600 may include one or more of the characteristics of thevarious processes described above with reference to process 2700. Forbrevity, these details are not repeated in the descriptions of the otherprocesses. The various methods and techniques described above withreference to method 2700 may be optionally implemented as one or morehardware units, such as those described with regard to FIG. 5B.

The units of FIG. 28 may be used to implement the various techniques andmethods described above with respect to FIGS. 25-27.

As shown in FIG. 28, an electronic device 2800 includes a display unit2802 configured to display a user interface, and, optionally: atouch-sensitive surface unit 2804 configured to receive user contacts,one or more sensor units 2806 configured to detect intensity of toucheswith the touch-sensitive surface unit; and a processing unit 2808coupled to the display unit 2802, the touch-sensitive surface unit 2804,and the sensor units 2806. In some embodiments, the processing unit 2808includes a display enabling unit 2810, a receiving unit 2812, and adetermining unit 2814.

In some embodiments, the display enabling unit 2810 is configured tocause a display of a notification, alert information, or user interface(or portions of a user interface) in conjunction with the display unit2802. For example, the display enabling unit 2810 may be used for:displaying a notification, replacing a first notification with a secondnotification on the display, displaying a user interface for selectingone of a plurality of message-processing operations.

In some embodiments, the receiving unit 2812 is configured to receivealerts, data, or information. For example, the receiving unit 2812 maybe used for receiving an alert comprising information.

In some embodiments, the determining unit 2814 is configured to makedeterminations. For example, the determining unit 2814 may be used for:determining whether a signal has been received within a predeterminedtime interval after a perceptual output; and determining whether thecharacteristic intensity of the second contact is above a thresholdintensity.

FIG. 29 shows a functional block diagram of an electronic device 2900configured in accordance with the principles of the various describedembodiments. The functional blocks of the device are, optionally,implemented by hardware, software, or a combination of hardware andsoftware to carry out the principles of the various describedembodiments. It is understood by persons of skill in the art that thefunction blocks described in FIG. 29 are, optionally, combined orseparated into sub-blocks to implement the principles of the variousdescribed embodiments. Therefore, the description herein optionallysupports any possible combination or separation or further definition ofthe functional blocks described herein.

As shown in FIG. 29, an electronic device 2900 includes a display unit2902 configured to display a graphic user interface, a haptic mechanismunit 2904 configured to issue haptic outputs, and a processing unit 2908coupled to the display unit 2902 and haptic mechanism unit 2904. In someembodiments, the electronic device optionally includes a touch-sensitivesurface unit 2926 configured to receive touch inputs and coupled to thedisplay unit 2902 and processing unit 2908. In some embodiments, theelectronic device 2900 optionally includes a rotatable and depressibleinput unit 2906, a microphone unit 2926, and a button unit 2928. In someembodiments, the processing unit 2908 optionally includes a receivingunit 2910, a perceptual output enabling unit 2912, a detecting unit2914, a determining unit 2916, a display enabling unit 2918, a launchingunit 2920, a sending enabling unit 2922, and an audio enabling unit2924.

Processing unit 2908 is configured to receive (e.g., with receiving unit2910) an alert including information, and, in response to receiving thealert, enable (e.g., with perceptual output enabling unit 2912) aperceptual output. Processing unit 2908 is further configured to detect(e.g., with detection unit 2914) a user input, determine (e.g., withdetermining unit 2916) whether the user input was detected within apredetermined time interval after the perceptual output, and, inaccordance with a determination that the user input was detected withinthe predetermined time interval, enable (e.g., with display enablingunit 2918) display of a notification on the display unit 2902, where thenotification comprises a first portion of the information.

In some embodiments, enabling the perceptual output includes causing thehaptic mechanism unit 2904 to issue a haptic output.

In some embodiments, processing unit 2908 is further configured to, inaccordance with a determination that the user input was detected afterthe predetermined time interval after the perceptual output, enable(e.g., with display enabling unit 2918) display of a clock face, wherethe clock face comprises an indication that the alert is unread.

In some embodiments, processing unit 2908 is further configured to, inaccordance with a determination that the user input was detected afterthe predetermined time interval after the perceptual output, enable(e.g., with display enabling unit 2918) display of a home screen on thedisplay unit 2902, where the home screen comprises a plurality of userinterface objects representing a plurality of applications, the userinterface objects, when activated, launching the correspondingapplication, and where the home screen comprises an indication that thealert is unread.

In some embodiments, enabling display of the notification comprisesactivating the display unit 2902 from an inactive state. In someembodiments, displaying the notification comprises replacing display ofa home screen with display of the notification. In some embodiments,enabling display of the notification comprises enabling display of ananimation that translates the notification onto the display in a firstdirection.

In some embodiments, the notification comprises an applicationaffordance for launching an application associated with the alert, andprocessing unit 2908 is further configured to detect (e.g., withdetecting unit 2914) a selection of the application affordance, and, inresponse to detecting the selection, launch (e.g., with launching unit2920) the application associated with the alert.

In some embodiments, processing unit 2908 is further configured to, inresponse to receiving the alert, determine (e.g., with determining unit2916) whether a user activity level meets an activity criteria, whereissuing the perceptual output is delayed until the user activity levelmeets the activity criteria.

In some embodiments, the electronic device is configured to detect(e.g., with detecting unit 2914) an intensity of contacts on thetouch-sensitive display (e.g., on touch-sensitive surface unit 2926),and processing unit 2908 is further configured to detect (e.g., withdetecting unit 2914) a contact on the touch-sensitive display while thenotification is displayed on display unit 2902 and determine (e.g., withdetermining unit 2916) whether the characteristic intensity of thecontact is above a threshold intensity. In some embodiments, processingunit 2908 is further configured to, in accordance with a determinationthat the characteristic intensity of the contact is above the thresholdintensity, enable (e.g., with display enabling unit 2918) display of anoption for suppressing one or more subsequent alerts that meet a mutecriteria. In some embodiments, processing unit 2908 is furtherconfigured to, in accordance with a determination that thecharacteristic intensity of the contact is below the thresholdintensity, and in accordance with a determination that the contact is ata location on the touch-sensitive display corresponding to theapplication affordance, launch (e.g., with launching unit 2920) theapplication associated with the alert. In some embodiments, the mutecriteria is based on the source of the alert.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a second contact on thetouch-sensitive display while the notification is displayed, determine(e.g., with determining unit 2916) whether the second contact meets adismissal criteria, and, in accordance with a determination that thesecond contact meets the dismissal criteria, enable (e.g., with displayenabling unit 2918) removal of the notification from the display. Insome embodiments, the second contact meets the dismissal criteria whenthe second contact comprises a swipe. In some embodiments, the secondcontact meets the dismissal criteria when the second contact comprises amovement of the second contact that exceeds a threshold distance.

In some embodiments, enabling display of the notification includesenabling display of an animation that translates the notification ontothe display unit in a first direction, and the second contact meets thedismissal criteria when the second contact comprises a movement of thecontact in a second direction opposite the first direction.

In some embodiments, the second contact includes a movement of thesecond contact and a release of the second contact, and processing unit2908 is further configured to, in response to detecting the movement ofthe second contact: enable (e.g., with display enabling unit 2918) thesliding of the notification on the display in accordance with themovement of the second contact, and enable (e.g., with display enablingunit 2918) display of a dismissal indicator adjacent to thenotification. Optionally, processing unit 2908 is further configured to,in accordance with a determination that the second contact meets thedismissal criteria and in response to detecting the release of thesecond contact, enable (e.g., with display enabling unit 2918) removalof the dismissal indicator and the notification from the display.Optionally, processing unit 2908 is further configured to, in accordancewith a determination that the second contact does not meet the dismissalcriteria and in response to detecting the release of the second contact,enable (e.g., with display enabling unit 2918) display of an animationthat translates the notification back to its initial position on thedisplay and enable removal of the dismissal indicator from the display.

In some embodiments, removing the notification includes displaying ananimation that translates the notification off of the display in thesecond direction. In some embodiments, removing the notification fromthe display includes inactivating the display. In some embodiments,removing the notification from the display includes replacing display ofthe notification with display of a home screen, and the home screencomprises an indication that the alert is unread. In some embodiments,removing the notification from the display includes replacing display ofthe notification with display of a clock face, and the clock faceincludes an indication that the alert is unread.

In some embodiments, processing unit 2908 is further configured to:determine (e.g., with determining unit 2916) whether a second user inputhas been detected within a second predetermined time interval afterdisplaying the notification; in accordance with a determination that thesecond user input has been detected within the second predetermined timeinterval, enable (e.g., with display enabling unit 2918) removal of thenotification from the display; and in accordance with a determinationthat the second user input has not been detected within the secondpredetermined time interval, enable (e.g., with display enabling unit2918) display of a second portion of the information, where the secondportion is different from the first portion.

In some embodiments, processing unit 2908 is further configured to:determine (e.g., with determining unit 2916) whether the user inputcontinues to be detected after a second predetermined time intervalafter displaying the notification; in accordance with a determinationthat the user input continues to be detected after the secondpredetermined time interval, enable (e.g., with display enabling unit2918) display of a second portion of the information on the displayunit, where the second portion is different from the first portion; andin accordance with a determination that the user input does not continueto be detected after the second predetermined time interval, enable(e.g., with display enabling unit 2918) removal of the notification fromthe display unit.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a third contact on thetouch-sensitive display (e.g., on touch-sensitive surface unit 2926)while displaying the notification, and, in response to detecting thethird contact, enable (e.g., with display enabling unit 2918) display onthe display unit 2902 of a second portion of the information, and thesecond portion is different from the first portion. In some embodiments,the second portion is displayed adjacent to the notification. In someembodiments, the third contact is a swipe in the first direction, andenabling display of the second portion of the information comprisessliding the second portion of the information onto the screen in thefirst direction.

In some embodiments, enabling display of the second portion of theinformation further includes obtaining (e.g., with receiving unit 2910)configuration data indicating whether to display the second portion ofthe information and enabling display of the second portion of theinformation in response to a determination that the configuration dataindicates that the second portion of the information should bedisplayed.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a selection of the applicationaffordance while displaying the notification, and launch (e.g., withlaunching unit 2920) an application associated with the alert inresponse to detecting the fourth contact.

In some embodiments, the alert is an electronic message, and theprocessing unit is further configured to detect (e.g., with detectingunit 2914) a fourth contact on the touch-sensitive display while thesecond portion of the information is displayed, and, in response todetecting the fourth contact, enable (e.g., with display enabling unit2918) display, on the display unit, of at least a portion of a messageconversation including electronic messages sent to and received from asource of the electronic message.

In some embodiments, the alert includes audio content, displaying thesecond portion of the information includes displaying an option to playthe audio content, and processing unit 2908 is further configured to:detect (e.g., with detecting unit 2914) a selection of the option toplay the audio content; and enable (e.g., with audio enabling unit 2924)playing of the audio content in response to detecting the selection. Insome embodiments, the audio content is a first audio content, andprocessing unit 2908 is further configured to receive (e.g., withreceiving unit 2910) a second alert comprising second audio contentafter detecting the selection of the option to play the first audiocontent and enable (e.g., with audio enabling unit 2924) playing of thesecond audio content in response to receiving the second alert.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a third user input whiledisplaying the second portion of the information and, in response todetecting the third user input, enable (e.g., with display enabling unit2918) scrolling of the second portion of the information in accordancewith the third user input. In some embodiments, the third user input isa swipe on the touch-sensitive display (e.g., on touch-sensitive surfaceunit 2926). In some embodiments, the third user input is a rotation ofthe rotatable and depressible input unit 2906.

In some embodiments, the third user input is associated with a downwarddirection, and the processing unit 2908 is further configured todetermine (e.g., with determining unit 2916) whether a beginning of theinformation is displayed on the display unit 2902, and in accordancewith a determination that the beginning of the information is displayedand in response to detecting the third user input, enable (e.g., withdisplay enabling unit 2918) removal of the second portion of theinformation from the display unit.

In some embodiments, the third user input is associated with an upwarddirection, and the processing unit 2908 is further configured todetermine (e.g., with determining unit 2916) whether an end of theinformation is displayed and, in accordance with a determination thatthe end of the information is displayed on the display unit 2902 and inresponse to detecting the third user input, enable (e.g., with displayenabling unit 2918) display of a first plurality of user interfaceobjects on the display unit. Optionally, the user interface objects areassociated with actions corresponding to an application associated withthe alert. In some embodiments, the first plurality of user interfaceobjects are scrolled upward onto the display below the end of theinformation as the information is scrolled upwards on the display unit.

In some embodiments, enabling removal of the second portion of theinformation from the display unit includes enabling replacement of thedisplay, on the display unit, of the second portion of the notificationwith a display, on the display unit, of a home screen comprising anindication of the time, and the home screen is displayed without anindication that the alert is unread. In some embodiments, enablingremoval of the second portion of the information includes enablingsliding the second portion of the information off of the display unit inthe second direction.

In some embodiments, the electronic device is configured to detect anintensity of contacts on the touch-sensitive display (e.g., ontouch-sensitive surface unit 2926), and processing unit 2908 is furtherconfigured to detect (e.g., with receiving unit 2914) a fifth contact onthe touch-sensitive display, and determine (e.g., with determining unit2916) whether the characteristic intensity of the fifth contact is abovea threshold intensity. In some embodiments, processing unit 2908 isfurther configured to: in accordance with a determination that thecharacteristic intensity of the fifth contact is above the thresholdintensity, enable (e.g., with display enabling unit 2918) display, ondisplay unit 2902, of a first plurality of user interface objects, wherethe user interface objects are associated with actions corresponding tothe application associated with the alert; and in accordance with adetermination that the characteristic intensity of the fifth contact isbelow the threshold intensity, launch (e.g., with launching unit 2920)an application associated with the alert.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a selection of a first userinterface object in the first plurality of user interface objects and,in response to detecting the selection of the first user interfaceobject, enable (e.g., with sending enabling unit 2922) sending of datato an external electronic device to cause the external electronic deviceto launch (e.g., with launching unit 2920) the application associatedwith the alert.

In some embodiments, processing unit 2908 is further configured todetermine (e.g., with determining unit 2916) whether user input has beenreceived within a third predetermined time interval while the secondportion of the information is displayed and, in accordance with adetermination that no user input has been received within the thirdpredetermined time interval, inactivate (e.g., with display enablingunit 2918) the display unit 2902.

In some embodiments, the notification is displayed on display unit 2902adjacent to the second portion of the information, the notificationincludes an application affordance, and processing unit 2908 is furtherconfigured to detect (e.g., with receiving unit 2914) a selection of theapplication affordance while the second portion of the information isdisplayed and, in response to detecting the selection of the applicationaffordance, enable (e.g., with display enabling unit 2918) display of asecond plurality of user interface objects on the display unit.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with receiving unit 2914) a selection of a first userinterface object of the second plurality of user interface objects and,in response to detecting the selection of the first user interfaceobject, enable (e.g., with display enabling unit 2918) display of athird plurality of user interface objects on the display unit.

In some embodiments, processing unit 2908 is further configured todetect an input on the button unit 2928 and, in response to detectingthe input on the button unit 2928, enable (e.g., with display enablingunit 2918) display of a third plurality of user interface objects on thedisplay unit.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with receiving unit 2914) a selection of a first userinterface object of the third plurality of user interface objects and,in response to detecting the selection of the first user interfaceobject of the third plurality of user interface objects, enable (e.g.,with display enabling unit 2918) display of a user interface forselecting a predefined response message on the display unit.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with receiving unit 2914) a selection of a firstpredefined response message and, in response to detecting the selectionof the first predefined response message, enable (e.g., with sendingenabling unit 2922) sending of the first predefined response message toa source of the alert.

In some embodiments, sending the first predefined response message tothe source of the alert includes displaying a confirmation affordance,detecting a selection of the confirmation affordance, and, in responseto detecting the selection of the confirmation affordance, enablingsending of the first predefined response message to the source of thealert.

In some embodiments, processing unit 2908 is further configured to,after enabling sending of the first predefined response message to thesource, enable (e.g., with display enabling unit 2918) display of amessage-sent confirmation screen on the display unit and enablereplacement of the display of the message-sent confirmation screen withdisplay of the home screen, where the home screen is displayed, on thedisplay unit, without an indication that the alert is unread.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with receiving unit 2914) a selection of a second userinterface object of the third plurality of user interface objects and,in response to detecting the selection of the second user interfaceobject of the third plurality of user interface objects, enable (e.g.,with display enabling unit 2918) display of a user interface forselecting an emoji icon on the display unit.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with receiving unit 2914) a selection of a first emojiicon and, in response to detecting the selection of the first emojiicon, enable (e.g., with sending enabling unit 2922) sending the firstemoji icon to the source of the alert. In some embodiments, enablingsending of the emoji icon to the source of the alert includes enablingdisplay of a confirmation affordance on the display unit 2902, detectinga selection of the confirmation affordance, and, in response todetecting the selection of the confirmation affordance, enabling sendingof the emoji icon to the source of the alert.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with receiving unit 2914) a selection of a second userinterface object of the second plurality of user interface objects and,in response to detecting the selection of the second user interfaceobject of the second plurality of user interface objects: determine(e.g., with determining unit 2916) whether the second portion of theinformation was displayed on the display unit 2902; in accordance with adetermination that the second portion of the information was displayed,enable (e.g., with display enabling unit 2918) display of the homescreen on the display unit, where the home screen is displayed withoutan indication that the alert is unread; and in accordance with adetermination that the second portion of the information was notdisplayed, enable (e.g., with display enabling unit 2918) display of thehome screen, where the home screen comprises an indication that thealert is unread.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with receiving unit 2914) a selection of a second userinterface object of the second plurality of user interface objects, and,in response to detecting the selection of the second user interfaceobject of the second plurality of user interface objects: determine(e.g., with determining unit 2916) whether the second portion of theinformation was displayed on the display unit 2902; in accordance with adetermination that the second portion of the information was displayed,enable (e.g., with display enabling unit 2918) display of the clockface, where the clock face is displayed without an indication that thealert is unread; and in accordance with a determination that the secondportion of the information was not displayed, enable (e.g., with displayenabling unit 2918) display of the clock face, where the clock facecomprises an indication that the alert is unread.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with receiving unit 2914) a selection of a third userinterface object of the second plurality of user interface objects and,in response to detecting the selection of the third user interfaceobject of the second plurality of user interface objects, enable (e.g.,with display enabling unit 2918) display of a virtual keyboard on thedisplay.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a selection of a fourth userinterface object of the second plurality of user interface objects and,in response to detecting the selection of the fourth user interfaceobject of the second plurality of user interface objects: enable (e.g.,with audio enabling unit 2924) recording of an audio input from themicrophone unit and enable (e.g., with sending enabling unit 2922)sending of data corresponding to the recorded audio input to the sourceof the alert.

In some embodiments, enabling sending of the data corresponding to therecorded audio input includes enabling display (e.g., using displayenabling unit 2918) of an indication of the recorded audio input and asend affordance on the display unit, detecting a selection of the sendaffordance, and, in response to detecting the selection of the sendaffordance, enabling sending of the data corresponding to the recordedaudio input to the source of the alert.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a depression of the rotatableand depressible input unit 2906 after launching the application, andenable (e.g., with display enabling unit 2918) display of the homescreen on the display unit in response to detecting the depression.

In some embodiments, the rotatable and depressible input unit 2906 is amechanical button that is rotatable, and the depression represents apress on the mechanical button. In some embodiments, the rotatable anddepressible input unit 2906 is a capacitive button that is rotatable,and the depression represents a touch on the capacitive button.

In some embodiments, the notification is a first notification, andprocessing unit 2908 is further configured to receive (e.g., withreceiving unit 2910) a second alert comprising second information whilethe first notification is displayed on the display unit 2902, and, inresponse to receiving the second alert, enable (e.g., with displayenabling unit 2918) replacement of display of the first notificationwith display of a second notification on the display unit, where thesecond notification comprises a first portion of the second information.

In some embodiments, processing unit 2908 is further configured toenable (e.g., with perceptual output enabling unit 2912) a secondperceptual output in response to receiving the second alert.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a request to dismiss the secondnotification and, in response to detecting the request, enable (e.g.,with display enabling unit 2918) dismissal of the second notificationand enable re-display of the first notification on the display unit2902.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a request to dismiss the secondnotification and, in response to detecting the request, enable dismissalof the second notification and enable (e.g., with display enabling unit2918) display of the home screen on the display unit, where the homescreen comprises an indication that the first alert and the second alertare unread.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a request to dismiss the secondnotification and, in response to detecting the request, enable dismissalof the second notification and enable (e.g., with display enabling unit2918) display of the clock face on the display unit 2902, where theclock face comprises an indication that the first alert and the secondalert are unread.

In some embodiments, processing unit 2908 is further configured toreceive (e.g., with receiving unit 2910) a second alert comprisingsecond information while displaying the second portion of theinformation, and, in response to receiving the second alert, enable(e.g., with display enabling unit 2918) replacement of display of thesecond portion of the information with display of a second notificationon the display unit 2902, where the second notification comprises afirst portion of the second information.

In some embodiments, the alert is a first alert received from a source,and processing unit 2908 is further configured to receive (e.g., withreceiving unit 2910) a second alert from the source while displaying thesecond portion of the information, and enable (e.g., with displayenabling unit 2918) display of a grouped notification representing thefirst alert and the second alert in response to receiving the secondalert. In some embodiments, the first alert and the second alert areassociated with the same application.

In some embodiments, processing unit 2908 is further configured todetect (e.g., with detecting unit 2914) a sixth contact on the groupednotification and, in response to detecting the sixth contact, enable(e.g., with display enabling unit 2918) display, on the display unit, ofa list of alerts received from the source, where the list of alerts isassociated with the same application.

In some embodiments, the alert is a fitness alert, and processing unit2908 is further configured to, after a second predetermined timeinterval, enable (e.g., with display enabling unit 2918) replacement ofdisplay on the display unit 2902 of the notification with display of auser interface object representing a fitness achievement, and, after athird predetermined time interval, enable (e.g., with display enablingunit 2918) replacement of display on the display unit of the userinterface object with display of a second portion of the information,where the second portion is different from the first portion.

The operations described above with reference to FIG. 25 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.29. For example, receiving operation 2502, issuing operation 2504,detecting operation 2506, determining operation 2508, and displayingoperation 2510 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation or other movement of thedevice) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 30 shows a functional blockdiagram of an electronic device 3000 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the function blocks described in FIG. 30 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 30, an electronic device 3000 includes a display unit3002 configured to display a graphic user interface and a processingunit 3004 coupled to the display unit 3002. In some embodiments, theelectronic device optionally includes a touch-sensitive surface unit3016 configured to receive touch inputs and coupled to the display unit3002 and processing unit 3004. In some embodiments, the processing unit3004 optionally includes a receiving unit 3006, a determining unit 3008,a display enabling unit 3010, a detecting unit 3012, and a perceptualoutput enabling unit 3014.

Processing unit 3004 is configured to receive (e.g., with receiving unit3006) a plurality of alerts and, in response to receiving the pluralityof alerts, determine (e.g., with determining unit 3008) whether theplurality of alerts meet a grouping criteria. Processing unit 3004 isfurther configured to, in accordance with a determination that theplurality of alerts meet the grouping criteria, enable (e.g., withdisplay enabling unit 3010) display of a grouped notificationrepresenting the plurality of alerts on the display unit 3002, and, inresponse to a determination that the plurality of alerts do not meet thegrouping criteria, enable (e.g., with display enabling unit 3010)display of a plurality of notifications representing the plurality ofalerts on the display unit.

In some embodiments, the grouping criteria is based on one or morecriteria selected from the group consisting of: whether the plurality ofalerts are received from the same source; whether the plurality ofalerts exceeds a numeric threshold of alerts; whether the plurality ofalerts are associated with the same application; and whether theplurality of alerts are received within a predetermined time period.

In some embodiments, the plurality of alerts includes a first alert anda second alert that are received from the same source and are associatedwith the same application, the first alert and the second alert meet thegrouping criteria, the first alert comprises first information and thesecond alert comprises second information, and the display unit is atouch-sensitive display unit. In some embodiments, processing unit 3004is further configured to detect (e.g., with detecting unit 3012) aseventh contact on the touch-sensitive display unit (e.g., ontouch-sensitive surface unit 3016) at a location corresponding to thegrouped notification and, in response to detecting the seventh contact,enable (e.g., with display enabling unit 3010) display of the firstinformation and the second information on the display unit 3002.

In some embodiments, the first alert and the second alert are receivedfrom different sources and are associated with the same application andprocessing unit 3004 is further configured to detect (e.g., withdetecting unit 3012) an eighth contact on the touch-sensitive displayunit (e.g., on touch-sensitive surface unit 3016) at a locationcorresponding to the grouped notification and, in response to detectingthe eighth contact, enable (e.g., with display enabling unit 3010)display, on the display unit 3002, of a list of alerts associated withthe application, where the list of alerts comprises the first alert andthe second alert.

In some embodiments, the plurality of alerts are associated with aplurality of applications, and where the plurality of alerts meets thegrouping criteria, where the display unit is a touch-sensitive displayunit, and processing unit 3004 is further configured to enable (e.g.,with display enabling unit 3010) display of a grouped notificationrepresenting the plurality of alerts, detect (e.g., with detecting unit3012) a ninth contact on the touch-sensitive display at a locationcorresponding to the grouped notification, and, in response to detectingthe ninth contact, enable (e.g., with display enabling unit 3010)display of a list of notifications representing the plurality of alerts,where the received alerts comprise the first alert and the second alert.

In some embodiments, processing unit 3004 is further configured toenable (e.g., with perceptual output enabling unit 3014) a perceptualoutput in further response to receiving the plurality of alerts. In someembodiments, processing unit 3004 is further configured to, further inaccordance with a determination that the plurality of alerts meets thegrouping criteria, enable (e.g., with perceptual output enabling unit3014) a single perceptual output and, further in accordance with adetermination that the plurality of alerts does not meet the groupingcriteria, enable (e.g., with perceptual output enabling unit 3014) aplurality of perceptual outputs corresponding to the plurality ofalerts.

The operations described above with reference to FIG. 26 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.30. For example, receiving operation 2602, determining operation 2604,detecting operation 2606, and displaying operations 2608 and 2610 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationor other movement of the device) corresponds to a predefined event orsub-event, such as selection of an object on a user interface, orrotation of the device from one orientation to another. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally uses or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 31 shows a functional blockdiagram of an electronic device 3100 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the function blocks described in FIG. 31 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 31, an electronic device 3100 includes atouch-sensitive display unit 3102, configured to receive contacts anddisplay a graphic user interface, and a processing unit 3104 coupled tothe display unit 3102. In some embodiments, the processing unit 3104optionally includes a receiving unit 3106, a display enabling unit 3108,and a detecting unit 3110.

Processing unit 3104 is configured to receive (e.g., with receiving unit3106) an alert comprising information while the display unit is activelydisplaying content, and, in response to receiving the alert, enable(e.g., with display enabling unit 3108) display of a notification banneracross a portion of the touch-sensitive display unit 3102, where thenotification banner comprises a first portion of the information andwhere at least a portion of the content continues to be displayed.Processing unit 3104 is further configured to detect (e.g., withdetecting unit 3110) a contact on the touch-sensitive display unit at alocation corresponding to the notification banner and enable (e.g., withdisplay enabling unit 3108) display, on the display unit, of a secondportion of the information in response to detecting the contact, wherethe second portion is different from the first portion.

The operations described above with reference to FIG. 27 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.31. For example, receiving operation 2702, displaying operations 2704and 2708, and detecting operation 2706 are, optionally, implemented byevent sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface (or whether rotation or othermovement of the device) corresponds to a predefined event or sub-event,such as selection of an object on a user interface, or rotation of thedevice from one orientation to another. When a respective predefinedevent or sub-event is detected, event recognizer 180 activates an eventhandler 190 associated with the detection of the event or sub-event.Event handler 190 optionally uses or calls data updater 176 or objectupdater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

The foregoing descriptions, for purpose of explanation, have beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. An electronic device, comprising: atouch-sensitive display; one or more processors; a memory; and one ormore programs, wherein the one or more programs are stored in the memoryand configured to be executed by the one or more processors, the one ormore programs including instructions for: while the display is activelydisplaying content, receiving an alert comprising information; inresponse to receiving the alert, displaying a notification banner acrossa portion of the display while at least a portion of the contentcontinues to be displayed on the display, wherein the notificationbanner comprises a first portion of the information; detecting a contacton the display at a location corresponding to the notification banner;and in response to detecting the contact, displaying a second portion ofthe information, wherein the second portion is different from the firstportion.
 2. The electronic device of claim 1, the one or more programsfurther including instructions for: displaying the notification banneracross a top portion of the display.
 3. The electronic device of claim1, the one or more programs further including instructions for: inresponse to receiving the alert while the display is actively displayingcontent, issuing a perceptual output.
 4. The electronic device of claim1, the one or more programs further including instructions for: inresponse to detecting the contact on the display, ceasing display of theactively displayed content by replacing display of the activelydisplayed content with display of the second portion of the information.5. The electronic device of claim 1, the one or more programs furtherincluding instructions for: in response to detecting the contact:launching an application associated with the alert; displaying theapplication on the touch-sensitive display; and opening the alert withinthe application.
 6. The electronic device of claim 1, wherein the firstportion of the information comprises a source of the alert.
 7. Theelectronic device of claim 1, wherein the first portion of theinformation comprises an identification of an application associatedwith the alert.
 8. The electronic device of claim 1, wherein the firstportion of the information comprises a time the alert was received. 9.The electronic device of claim 1, wherein the contact is a tap gesture.10. The electronic device of claim 1, wherein the contact is a swipegesture.
 11. The electronic device of claim 1, the one or more programsfurther including instructions for: displaying the notification bannerby displaying an animation that slides the notification banner in afirst direction onto the touch-sensitive display.
 12. The electronicdevice of claim 11, wherein the contact is a swipe gesture in the firstdirection of the animation, the one or more programs further includinginstructions for: in response to detecting the swipe gesture in thefirst direction, displaying the second portion of the information whilecontinuing to display at least a portion of the actively displayedcontent.
 13. The electronic device of claim 12, the one or more programsfurther including instructions for: detecting a second contact on thedisplay at a location corresponding to the second portion of theinformation, wherein the second contact is a second swipe gesture in anopposite direction of the first direction of the animation; and inresponse to detecting the second contact, sliding the second portion ofthe information in the opposite direction off of the display.
 14. Theelectronic device of claim 1, the one or more programs further includinginstructions for: while the display is actively displaying content,receiving a second alert comprising second information; in response toreceiving the second alert, displaying a second notification banneracross a portion of the display by displaying an animation that slidesthe second notification banner in a first direction onto the display,wherein the second notification banner comprises a first portion of thesecond information and wherein at least a portion of the activelydisplayed content continues to be displayed; detecting a third contacton the display at a second location corresponding to the secondnotification banner, wherein the third contact is a swipe gesture in anopposite direction of the first direction of the animation; and inresponse to detecting the third contact: dismissing the secondnotification banner by sliding the second notification banner in theopposite direction off of the display, and continuing to display theactively displayed content on the display.
 15. The electronic device ofclaim 1, the one or more programs further including instructions for:while the display is actively displaying content, receiving a thirdalert comprising third information; in response to receiving the thirdalert, displaying a third notification banner across a portion of thedisplay, wherein the third notification banner comprises a first portionof the second information and wherein at least a portion of the activelydisplayed content continues to be displayed; and removing display of thethird notification banner after lapse of a predetermined period of timewithout receiving user contact on the display.
 16. A non-transitorycomputer-readable storage medium storing one or more programs, the oneor more programs comprising instructions, which when executed by one ormore processors of an electronic device with a display, cause the deviceto: while the display is actively displaying content, receive an alertcomprising information; in response to receiving the alert, display anotification banner across a portion of the display while at least aportion of the content continues to be displayed on the display, whereinthe notification banner comprises a first portion of the information;detect a contact on the display at a location corresponding to thenotification banner; and in response to detecting the contact, display asecond portion of the information, wherein the second portion isdifferent from the first portion.
 17. A method, comprising: at anelectronic device with a touch-sensitive display: while the display isactively displaying content, receiving an alert comprising information;in response to receiving the alert, displaying a notification banneracross a portion of the display while at least a portion of the contentcontinues to be displayed on the display, wherein the notificationbanner comprises a first portion of the information; detecting a contacton the display at a location corresponding to the notification banner;and in response to detecting the contact, displaying a second portion ofthe information, wherein the second portion is different from the firstportion.